OFAC Sanctions Afghanistan: Compliance & License Guide

Unlicensed transactions with designated persons trigger both criminal and civil liability. Civil penalties reach the greater of $356,579 per violation or twice the transaction value under the International Emergency Economic Powers Act (IEEPA). Criminal violations: fines up to $1 million and up to 20 years imprisonment for willful breaches under 50 U.S.C. § 1705.

The Taliban received SDGT designation under Executive Order 13224 on July 2, 1999, reimposed following their August 2021 return to power. The Haqqani Network carries dual designation—SDGT under E.O. 13224 (September 2012) and FTO under INA § 219. Both trigger automatic asset freezes and transaction prohibitions for all U.S. persons: individuals, corporations, branches, and foreign subsidiaries that are 50% or more U.S.-owned.

OFAC enforces strict liability. Intent doesn’t matter for civil penalties; reckless disregard or negligent failure to screen suffices. The 2023 OFAC Enforcement Guidelines do offer some relief for voluntary self-disclosure, remedial steps, and effective compliance programs—but only if you catch the violation yourself. OFAC discovers it during an exam? No voluntary disclosure credit, period.

When a transaction involves a blocked person, you must freeze property and file a report within 10 business days via OFAC’s online system. Failure to block or file constitutes separate violations with independent penalties. For Afghanistan deals, that blocking obligation covers funds, goods in transit, and accounts receivable if the counterparty is on the SDN List or owned 50%+ by someone blocked.

OFAC publishes the Specially Designated Nationals (SDN) List daily at 8:00 AM EST in PDF, XML, and CSV formats. It includes Taliban officials, Haqqani commanders, Afghan government ministers, and associated entities designated under E.O. 13224. Afghanistan entries carry program codes SDGT, SDNTK (Specially Designated Narcotics Traffickers), and AFGHAN for individuals subject to Afghanistan-specific sanctions under prior United Nations Security Council resolutions.

Before executing any transaction, match customer names, business counterparties, and beneficial owners against the SDN List. OFAC’s Sanctions List Search tool offers a web interface with adjustable confidence thresholds—from exact matches (100% confidence) to approximate string matching for name variations and transliterations common in Afghan names.

Best-practice workflows break down like this:

The Consolidated Sanctions List combines SDN entries with non-SDN program-specific lists: the Foreign Sanctions Evaders List, Sectoral Sanctions Identifications List, and Non-SDN Menu-Based Sanctions List. Afghanistan transactions require screening against the full Consolidated List, not just the SDN List, to catch sectoral restrictions and indirect entity controls.

XML and CSV formats enable automated batch screening for high-volume institutions. Financial institutions typically embed OFAC screening into payment processing systems, blocking transactions automatically when matches exceed confidence thresholds. Compliance officers then manually review borderline cases and false positives before clearing payments.

Effective OFAC compliance requires more than a checklist. You need documented policies, trained personnel, and third-party verification systems that go beyond list screening. OFAC’s Framework for Compliance Commitments (May 2019) identifies five essential components: management commitment, risk assessment, internal controls, testing and audit, and training.

Management commitment starts at the board level. Senior leadership must allocate real resources, designate a compliance officer with direct board access, and establish written policies addressing Afghanistan-specific risks. Your board should review program effectiveness at least annually and formally document resolutions authorizing Afghanistan operations—this documentation matters if regulators audit you later.

Risk assessment forces you to identify where exposure actually lives. Which transaction types create heightened OFAC risk? Correspondent banking for Afghan financial institutions tops the list. Supply chain relationships with Afghan government contractors rank high. Humanitarian aid delivery requiring Taliban ministry coordination creates its own complications. Update your risk assessment whenever OFAC issues new designations or modifies General Licenses—which happens more often than you’d expect.

Internal controls translate risk into action. Afghanistan compliance typically requires:

Testing and audit prove your controls work. Independent auditors or internal teams should test screening accuracy, license documentation, and recordkeeping at least annually. Audit findings require management-approved remediation plans with real deadlines.

Training ensures your staff actually understands what they’re doing. Coverage should include SDN List screening procedures, General License applicability, blocked property reporting deadlines, and red flags signaling potential evasion. Annual refreshers keep people current as new designations and regulatory changes roll out.

Record retention under 31 CFR § 501.901 mandates preserving screening documentation, license applications, and compliance records for five years minimum. Electronic systems should capture screening parameters, match results, and reviewer decisions—you’ll need this detail if audits come.